$ TYPE SYS$UPDATE:CDDRLSE.MEM











                            CHAPTER 1

                          RELEASE NOTES



1.1  NEW FEATURES OF CDD VERSION 3.1

The following sections describe the new features of the
Dictionary Management Utility (DMU), the Verify/Fix Utility
(CDDV), and the CDD Data Definition Language Utility (CDDL).



1.1.1  New Features Of DMU

New features of the Dictionary Management Utility include:

o  Support for the VAX/VMS Version 4.0 User Identification Code
   changes.  The SET PROTECTION, SET PROTECTION/EDIT, and
   LIST/PROTECTION commands can now authorize users by three
   types of rights identifiers.  You can specify the traditional
   numeric UIC; now each of its two parts can contain up to 5
   octal digits.  With VAX/VMS Version 4.0 you can also specify
   an alphanumeric UIC or an alphanumeric rights identifier.  A
   rights identifier matches all users defined in the rights
   database as members of a group.  The SET PROTECTION/EDIT
   screen layout has changed format, and the UIC field is now
   labelled RIGHTS.  The LIST/PROTECTION command reflects these
   two new ways to specify users.

   For more information about SET PROTECTION, see Section 2.18 of
   The VAX Common Data Dictionary Utilities Reference Manual.
   For more information about SET PROTECTION/EDIT, see Section
   2.19.

o  SET/PROTECTION has a new qualifier, /RIGHTS.  /RIGHTS is
   identical to /UIC, and you can use the two interchangeably.
   For more information, see Section 2.18 of the VAX Common Data
   Dictionary Utilities Reference Manual.




                                 1-1

























RELEASE NOTES


o  You can set a limit to the number of versions of an object
   that can be created.  You define the logical name
   CDD$VERSION_LIMIT at the system, group, or process level.  If
   different version limits are defined at different levels, the
   minimum number prevails, whether it is defined by a system,
   group, or process logical name.  For more information about
   CDD$VERSION_LIMIT, see Section 2.13 of the VAX Common Data
   Dictionary Utilities Reference Manual and Section 2.3.3 of the
   VAX Common Data Dictionary User's Guide.

o  A new command, RENAME/SUBDICTIONARY, changes the file
   specification to which a subdictionary directory points.  You
   can set the directory to point to a subdictionary file if you
   are moving or renaming it.  It is no longer necessary to
   delete and then recreate the directory.  For detailed
   information about RENAME/SUBDICTIONARY, see Section 2.14 of
   the VAX Common Data Dictionary Utilities Reference Manual.

o  The /AUDIT qualifier now provides a default explanation when
   you use it with the following commands:  BACKUP, COPY,
   EXTRACT, RENAME, RENAME/SUBDICTIONARY and RESTORE.




1.1.2  New Feature Of The CDD Verify/Fix Utility (CDDV)


o  New messages to explain syntax errors.  If you make a syntax
   error when entering a CDDV command, CDDV now gives you more
   precise information about the nature of the error and how to
   correct it.




1.1.3  New Features Of CDDL

New features of the CDD Data Definition Language Utility (CDDL)
include:

o  VAX COBOL now supports the CDDL INDEXED FOR COBOL BY clause.
   In addition, the DMU EXTRACT/RECORD command and the CDDL
   /COPY_LIST qualifier, which create source text from CDDL
   record definitions, now recognize the INDEXED FOR COBOL BY
   clause.  For more information on this clause, see Sections
   2.17 and 2.18 of the VAX Common Data Dictionary Data
   Definition Language Reference Manual.





                                 1-2






















                                                         RELEASE NOTES


1.2  CDD VERSION 3.1 AND VAX/VMS VERSION 4.0

You can install CDD Version 3.1 only on a VAX/VMS Version 4.0 or
higher system.



1.2.1  Installing CDD On A Cluster

If you are using CDD Version 3.1 on a VAX/VMS Version 4.x
cluster, you should install the main dictionary file (CDD.DIC) on
a device which is accessible to the entire cluster.  Otherwise,
you may get some unnecessary lock conflicts between systems.

You should also make sure that all system logical names,
including CDD$DICTIONARY, which is used to identify dictionary
files, translate in the same way on each system in the cluster.
Otherwise, the same subdictionary directory may point to several
different dictionary files, or you may receive a CDD error that
several subdictionary directories point to the same subdictionary
file.

The file CDDCPLINS.COM is no longer part of the kit.  The
installation procedure does not differentiate between a regular
installation and an installation on an alternate root.

The installation procedure places CDD.DIC in SYS$COMMON:[SYSEXE]
if all the following conditions are met:

      o  You are installing on a cluster.

      o  You specify SYS$SYSTEM as the location of
         CDD$DICTIONARY.

      o  You have no existing CDD.DIC file in any of the
         directories in the SYS$SYSTEM search list.


Note that in all other circumstances, CDD places a new dictionary
in the first device:directory specification in the search list.

If you are installing on a cluster, VMSINSTAL places your
CDDSTRTUP.COM file in SYS$COMMON:[SYSMGR].



1.2.2  Search Lists

Wherever you can use a logical name, you can also specify a
search list that lists possible alternative locations for a file.
The CDD then creates the file in the first available location.


                                 1-3






















RELEASE NOTES


If the file has already been created, the CDD finds and opens it.
For further information on using a search list, see Section 2.3
of the VAX Common Data Dictionary Utilities Reference Manual and
also the Installation Guide/Release Notes.



1.2.3  New VAX/VMS Protection Features

VAX/VMS Version 4.0 provides two new security features:

      o  Rights Database

         You can define access privileges and user groups
         associated with these privileges, and store this
         information in a rights database.

      o  DCL EDIT/ACL Command for File Protection

         The DCL EDIT/ACL Command provides a new way to set
         protection on VMS files such as your root dictionary
         file and subdictionary files.


For further information about the rights database and EDIT/ACL,
see Chapter 4 of the VAX Common Data Dictionary User's Guide and
VAX/VMS Version 4.x documentation.



1.3  NEW LANGUAGES SUPPORTING CDD


o  VAX C, Version 2.0 and later

o  VAX FORTRAN, Version 4.0 and later

o  VAX PASCAL, Version 3.0 and later




1.4  UNDERSCORE PRECEDING CDD$TOP

In Version 3.1, you may temporarily define a logical name for
CDD$TOP.  (See Section 8.3.1 of the VAX Common Data Dictionary
User's Guide for a description of the circumstances under which
you might define a logical name for CDD$TOP.)

In pathnames displayed on the terminal, CDD Version 3.1 places an
underscore before CDD$TOP.  The name CDD$TOP is always translated


                                 1-4






















                                                         RELEASE NOTES


at least once.  After the final translation, CDD$TOP will
automatically be preceded by an underscore (_CDD$TOP).

If a logical name translates to an absolute pathname, then
CDD$TOP will be translated again.  For example, CDD$DEFAULT might
translate to CDD$TOP.JONES.  Then CDD$TOP is translated a final
time to _CDD$TOP.



1.5  USING MULTIPLE VERSIONS OF CDD OBJECTS WITH VAX DATATRIEVE

With CDD Versions 3.0 and later, you can create multiple versions
of dictionary objects.  If you are using VAX DATATRIEVE, however,
you need VAX DATATRIEVE Version 3.0 to access multiple versions
of CDD objects.  Earlier versions of VAX DATATRIEVE do not
support multiple versions.



1.6  VAX DBMS AND CDDEXC.EXE

VAX DBMS keeps the CDD message file (CDDEXC.EXE) open while VAX
DBMS is running.  Therefore, even though a new file is installed
as part of the CDD installation procedure, the old file remains
in place until you shut down VAX DBMS.  You should shut down VAX
DBMS before installing the CDD and start VAX DBMS again after the
CDD has been installed.  See Section 1.4 of the VAX Common Data
Dictionary Installation Guide for more information.



1.7  INSTALLING CDD WITH SYSPRV

If you use the INSTALL utility to install a known image with the
qualifier /PRIVILEGED=(SYSPRV), you must install the associated
message file with the qualifier /SHARED.  Otherwise, the image
cannot access its own message file.  For example, if you install
DMU with SYSPRV, install DMUEXC.EXE, DMU's message file, with the
qualifier /SHARED.



1.8  PATH NAMES POINTING TO SUBDICTIONARY FILES

When you move a subdictionary file from one system to another,
make sure that the subdictionary's path name on the new system is
the same as it was on the old system.  Because both VAX
DATATRIEVE and VAX DBMS use full path names by default to locate
data definitions, changing the path name of a subdictionary will
produce errors when DATATRIEVE or DBMS tries to access


                                 1-5






















RELEASE NOTES


definitions in that subdictionary.

Currently, CDD does not check to ensure that subdictionary path
names remain unchanged.



1.9  THE CDDL ALIGNED CLAUSE

Be careful when you use the CDDL ALIGNED Clause.

o  You should not use the ALIGNED clause in template records.
   When CDDL stores the template record, the position of an
   aligned field is fixed within the record and is not changed
   when the record is copied into another record definition.
   Therefore, the newly created field may not align properly in
   the new record definition.

o  Records created with the ALIGNED clause using previous
   versions of CDDL may not have aligned fields properly.
   Version 3.1 corrects this alignment problem.  However, if you
   recompile the records using the ALIGNED clause, data already
   stored will no longer match the recompiled data definition.




1.10  COPYING AND RENAMING A DICTIONARY OBJECT PROTECTED BY A
      PASSWORD

Cases may occur where you are granted UPDATE and CONTROL
privileges for an object only through a password.  If this is
true, you cannot copy any version of another object with the same
name as the protected object to the directory of the protected
object, because DMU COPY provides no way to specify the protected
object's password.

In a case where you are granted the UPDATE privilege for an
object only through a password, you cannot rename another object
as a new version of the protected object, because DMU RENAME
provides no way to specify the protected object's password.












                                 1-6

